Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/ResearchCodingClub/python-testing-for-research/compare/md-outputs..md-outputs-PR-6

The following changes were observed in the rendered markdown documents:

 10-CI.md                               | 324 +++++++++++++++++++++++++--------
 fig/github_action.png (new)            | Bin 0 -> 97368 bytes
 fig/github_actions_button.png (new)    | Bin 0 -> 9092 bytes
 fig/github_repo_view.png (new)         | Bin 0 -> 35113 bytes
 fig/matrix_tests.png (new)             | Bin 0 -> 30443 bytes
 fig/pull_request_test_failed.png (new) | Bin 0 -> 50360 bytes
 files/10-CI/tests.yaml (new)           |  72 ++++++++
 md5sum.txt                             |   2 +-
 8 files changed, 319 insertions(+), 79 deletions(-)

⏱️ Updated at 2026-02-10 17:40:39 +0000

I've modified this lesson to talk about matrix jobs earlier, and to simplify the push/pull_request section. The exercise to engineer a situation in which push would pass but pull_request wouldn't has been left as the final exercise to the students, so not a huge problem if we run out of time for it.

Definitely a tricky concept to teach and create a lesson for - looks great!